Maybe this should have separate elements, like suggested in the Tabs PR. It doesn't do anything special with the insides of the table, so maybe we can just inject children and the end user can put normal table contents in it. That way you just replace <table> with <Table> and get material styling on it. Thoughts?

Material-ui originally went with a Table component that just had like over nine thousand configuration options for their initial version. However they split that up into a bunch of components that represent parts of a table (TableBody, TableRow, etc).

That way you just replace <table> with <Table> and get material styling on it.

There are some optional classes on table data cells, such as mdl-data-table__cell--non-numeric.
And the user could pass ReactElement as columns and rows also.

@coderhaoxin I think we should have separate components for rows, columns, etc

@phated

have separate components for rows, columns

done

I think the mapping needs to go away. A component library should just accept children, not custom DSLs of arrays of objects.